Skip to content

Conversation

@ivikash
Copy link
Member

@ivikash ivikash commented Oct 10, 2024

move getIndentedCode to textDocumentUtilities and use cwsprChatInteractionType from aws-toolkit-common


License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

@ivikash ivikash requested review from a team as code owners October 10, 2024 18:10
@github-actions
Copy link

This pull request modifies code in src/ but no tests were added/updated. Confirm whether tests should be added or ensure the PR description explains why tests are not required.

@ivikash ivikash changed the title refactor(amazonq): move getIndentedCode to textDocumentUtilities and use cwsprChatInteractionType from aws-toolkit-common refactor(amazonq): move getIndentedCode to textDocumentUtilities and use cwsprChatInteractionType Oct 10, 2024
* Indents the given code based on the current document's indentation at the selection start.
*
* @param {any} message - The message object containing the code.
* @param {vscode.TextDocument} doc - The VSCode document where the code is applied.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

non-blocker: This will make the value actually clickable in vscode when you hover the docstring and also if TextDocument were to be renamed this would automatically update. Note you need to add a string in between "param" and the {} or it doesnt render properly

Suggested change
* @param {vscode.TextDocument} doc - The VSCode document where the code is applied.
* @param - {@link vscode.TextDocument} doc - The VSCode document where the code is applied.

…use cwsprChatInteractionType

from aws-toolkit-common
@justinmk3 justinmk3 merged commit d33c256 into aws:master Oct 10, 2024
21 of 24 checks passed
tverney pushed a commit to tverney/aws-toolkit-vscode that referenced this pull request Oct 21, 2024
- move getIndentedCode to textDocumentUtilities
- use cwsprChatInteractionType from aws-toolkit-common
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants